-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[compatibility]Add skip_min_kubelet_versions #35949
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Siyuan Zhang <[email protected]>
9b2e83e to
c07740b
Compare
BenTheElder
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
/hold
I wonder if it might make sense to just skip all MinimumKubeletVersion to simplify for now, it's relatively few tests and the feature we're testing isn't aimed at kubelet.
We should probably come up with a better way to express this in Kubernetes, maybe we can do something smarter with ginkgo label filtering ... cc @pohly @aojea @SergeyKanzhelev
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, siyuanfoundation The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
If we are testing skip upgrade from 1.34 to 1.36, we would still want to test all the test cases with MinimumKubeletVersion=1.34. So I think skip all MinimumKubeletVersion would be too simplified. |
revert #35923 to use SKIP MinimumKubeletVersion instead